I've used startDXLTracing_ and its relative functions for suspending, resuming, and stopping the tracing for many years to help debug scripts. It has been very useful. There are times that I want to understand what the bottlenecks are that slow down scripts and from my experience with C and C++ know that profiling can be very useful here. I see that there are two functions, startDXLProfiling_ and stopDXLProfiling_ that hint at this capability. I have played around with these a bit but not very successfully. startDXLProfiling_ takes a string argument that when I populate with a file name and path creates the file, but this file does not get populated with anything as the script runs. Other profilers I have used output a list of functions and procedures with information about how much time was spent in those functions and procedures. Does anyone have any experience with using these profiling functions? Do they actually do anything or are they placeholders for possible future capabilities? Are there other function calls that are needed to make these work? Any help would be greatly appreciated. - David Bond David_G_Bond - Tue Jun 12 10:44:46 EDT 2018 |
Re: startDXLProfiling_ I need to admit, I tried getting them to work but I failed. I remembered something that this will only work, when DOORS is started in some special debug mode and they only give information regarding the performance of the DXL Execution Engine, not the DXL program itself. So from what I remember they were not very useful. However in recent DOORS versions there have been a LOT of new debugging functionalities implemented. I never came around to actually updating the perms list, but there are new data structures like "DebugVar", "Script", "Callback", etc. ... which might help you even more. Are you (or any other one reading this) maybe interested in a joined effort on exploring and publishing these - I currently do not want to spend any solo time on uncovering DOORS secrets. Regards, Mathias |